Add SSH key file specification instructions #42110
Conversation
Added instructions for manually specifying the SSH key file when connecting to GitHub, including example SSH command and expected output.
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
github-actions
bot
added
the
triage
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
This comment was marked as spam.
This comment was marked as spam.
|
@kmanwar89 Thanks for the issue and PR! This is a fairly substantial change, so I'll need to make sure this is where we would want it. |
Sharra-writes
added
content
htoothitlwin23-sudo
left a comment
htoothitlwin23-sudo
left a comment
There was a problem hiding this comment.
@badboy21l![Uploading 24580111...]
5 participants
Added instructions for manually specifying the SSH key file when connecting to GitHub, including example SSH command and expected output.
Why:
Closes: #42109
What's being changed (if available, include any code snippets, screenshots, or gifs):
Details have been added to advise a user to use the
-i <filename>command flag while troubleshooting the SSH connection in case they specified a non-default filename. For users that do specify a non-default filename, the SSH standard error (debug1: No more authentication methods to try; [email protected]: Permission denied (publickey).) is ambiguous and provides no guidance on what further troubleshooting steps to take. The edits to this article seek to address this gap.Check off the following: